home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
BBS Toolkit
/
BBS Toolkit.iso
/
doors_2
/
tview294.zip
/
NETWORK.DOC
< prev
next >
Wrap
Text File
|
1990-06-03
|
2KB
|
54 lines
This door is fully tested by multi-node systems. The door has performed
flawlessly under both Networks and Multitaskers.
If you are running PCBoard 14.5 you can run this door with a single
batch file and .CNF file for all nodes!
On my system I have three nodes. The default directories are called:
D:\PCB1
C:\PCB2
C:\PCB3
The variables needed are the drive letter and the node number, so I set
those in my environment by putting the following in my BOARD.BAT (on
node 1):
SET DRIVE=D:
SET NODE=1
For Node 2's BOARD.BAT it's:
SET DRIVE=C:
SET NODE=2
Node 3:
SET DRIVE=C:
SET NODE=3
Then I go into PCBSETUP and edit the DOORS.LST (aka DOORS.DAT) file to
define the path to the batch file. I use D:\DOORBATS.
I go to the \DOORBATS directory and create the door batch file. For a
Prokit door it would look something like this (node 1 used for example):
Batch file says: DOS Translates it to:
@ECHO OFF @ECHO OFF
D: D:
CD\PCB\DOORS CD\PCB\DOORS
DOOR DOOR.CNF %DRIVE%\PCB%NODE% DOOR DOOR.CNF D:\PCB1
%DRIVE% D:
CD\PCB%NODE% CD\PCB1
BOARD BOARD
This method makes it a cynch to install a door on any number of nodes.
the .CNF files for Prokit doors aren't node specific, so there is no
reason to have more than one of them. In the case of DOORPCH doors, you
need on .CFG file per node, but you can still point to them using the
%NODE% variable if you name them something like PCH1.CFG,
PCH2.CFG, etc. I'm running a large assortment of different doors, and
so far, all of them have installed using this method.